chore: depend on hotdata-framework (renamed from hotdata-runtime)#26
Conversation
There was a problem hiding this comment.
Clean, consistent rename of hotdata-runtime → hotdata-framework across dependabot, pyproject description, publish script, and guardrail tests. No stray references remain in either direction, and the guardrails correctly continue to enforce independence from the renamed package.
There was a problem hiding this comment.
Clean, consistent rename of hotdata-runtime → hotdata-framework across all files. No leftover references remain, and the guardrail tests still pass.
One note (non-blocking, about the PR description rather than the code): the title/body say this makes hotdata-ibis depend on hotdata-framework and update imports to hotdata_framework. The diff does the opposite — it keeps the architecture guardrails that forbid depending on / importing that package (the package depends on the hotdata SDK only). As a result the merge-order note (publish hotdata-framework to PyPI, then regenerate uv.lock) doesn't apply, since hotdata-framework is not a dependency — uv.lock only needs to track the version bump, which it already does (0.1.4 → 0.1.5). Worth correcting the description so the intent is clear; the code itself is correct.
Renames the dependency from
hotdata-runtimetohotdata-framework(same package, renamed) and updates imports tohotdata_framework.Merge order:
hotdata-frameworkmust be published to PyPI first; thenuv.lockhere needs regenerating (uv lock) before CIuv sync --lockedwill pass.